Walkthrough

A new board configuration header file was added for the AOCODARCG440_AIO target in Betaflight. The configuration defines the MCU type (STM32G47X), board identification, enabled peripheral features, pin mappings for motors, LEDs, UARTs, I2C, SPI and ADC, timer configurations, and default peripheral instance assignments.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

This is a straightforward addition of configuration data for a new board target. Review effort is primarily spent verifying pin mappings, feature assignments, and peripheral configurations match the hardware specifications and follow established conventions.

Suggested reviewers

• haslinghuis
• nerdCopter
• sugaarK

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Looks like the 4 motor pins are divided over 3 (!?) timers?

M1 -> PB0 -> TIM3 CH3
M2 -> PB1 -> TIM3 CH4
M3 -> PB9 -> TIM4 CH4
M4 -> PB2 -> TIM5 CH1

According to the current guidelines:

first 4 motors are required to use a 1 GPIO and one 4-channel timer.

(Emphesis mine.)

Edit:
If this was approved before the most recent motor requirements were in effect, please disregard the above.

Looks like the 4 motor pins are divided over 3 (!?) timers?

M1 -> PB0 -> TIM3 CH3 M2 -> PB1 -> TIM3 CH4 M3 -> PB9 -> TIM4 CH4 M4 -> PB2 -> TIM5 CH1

According to the current guidelines:

first 4 motors are required to use a 1 GPIO and one 4-channel timer.

(Emphesis mine.)

Edit: If this was approved before the most recent motor requirements were in effect, please disregard the above.

As long as the motors are on the same port for a FC using bitbang, it's fine. The G4 is somewhat limited in IO, so there aren't a lot of good options.